<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Dictionary changes: GNOME Data Access 5 manual</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="index.html" title="GNOME Data Access 5 manual">
<link rel="up" href="migration-2.html" title="Migration from 3.X versions">
<link rel="prev" href="ch08s03.html" title="GdaQuery and GdaCommand merge into GdaStatement">
<link rel="next" href="migration-2-exec.html" title="Statement execution">
<meta name="generator" content="GTK-Doc V1.32 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
<td><a accesskey="u" href="migration-2.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
<td><a accesskey="p" href="ch08s03.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="migration-2-exec.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="sect1">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="migration-2-dict"></a>Dictionary changes</h2></div></div></div>
<p>The GdaDict object has been removed and the <a class="link" href="GdaMetaStore.html" title="GdaMetaStore">GdaMetaStore</a> object introduced to
      replace it, but with slightly different features.</p>
<p>The GdaDict object used an XML file to store its data which imposed parsing potentially big XML files and creating its own
      internal structures from it (before discarding the XML tree) which was both CPU and memory intensive. Memory was
      also wasted as most of the time not all the dictionary would be exploited. The new 
      <a class="link" href="GdaMetaStore.html" title="GdaMetaStore">GdaMetaStore</a> object relies on a database (an SQLite file by default) to store its data
      which solves the problems mentioned above.</p>
<p>It was difficult for applications to add their own data in the dictionary (the API existed but was difficult to understand
      and use), this has been solved by allowing applications to create DBMS objects into the 
      <a class="link" href="GdaMetaStore.html" title="GdaMetaStore">GdaMetaStore</a>'s associated database.</p>
<p>There was a <span class="emphasis"><em>strange</em></span> relation between a GdaDict object and a 
      <a class="link" href="GdaConnection.html" title="GdaConnection">GdaConnection</a> object as a connection <span class="emphasis"><em>needed to</em></span> be assigned
      to a GdaDict object; this is not the case as now each <a class="link" href="GdaConnection.html" title="GdaConnection">GdaConnection</a> object builts
      a <a class="link" href="GdaMetaStore.html" title="GdaMetaStore">GdaMetaStore</a> when it needs it (providers implementations may benefit from it) and
      the user can provide his own <a class="link" href="GdaMetaStore.html" title="GdaMetaStore">GdaMetaStore</a> object when needed.</p>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.32</div>
</body>
</html>